SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 41503: PROC METALIB might not accurately report the correct number of tables analyzed

DetailsAboutRate It

If you specify both the PREFIX and FOLDER statements in the METALIB procedure and the name of at least one table in the library being analyzed begins with the same characters you specify as the PREFIX value, PROC METALIB will fail to report the correct number of tables analyzed in the printed output. For example, if your library has one table called MAY_REPORT and you submit the following PROC METALIB step:

proc metalib; omr (repname="Foundation" library="MyLib"); prefix="MAY_"; folder="/Shared Data/myfolder"; run;

the procedure will report that 0 tables were analyzed:

NOTE: A total of 0 tables were analyzed for library "MyLib". NOTE: Metadata for 0 tables was updated. NOTE: Metadata for 0 tables was added. NOTE: Metadata for 0 tables matched the data sources. NOTE: 0 other tables were not processed due to error or UPDATE_RULE.

Also, if you have specified the TracingLevel (TL) option on your PROC METALIB statement, you might see return code of -3 reported in your log:

(MSCMLB) addmeta: Exit; Return Code is -3

Note that PROC METALIB does actually correctly analyze the tables and update the metadata, so the messages are misleading.

To circumvent the problem, either do not specify the PREFIX statement or modify the value of the PREFIX so the character sequence is different from the names of any tables in the library.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Metadata Serverz/OS9.219.39.2 TS2M39.3 TS1M0
Microsoft® Windows® for 64-Bit Itanium-based Systems9.219.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.219.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.219.39.2 TS2M39.3 TS1M0
Microsoft Windows XP 64-bit Edition9.219.39.2 TS2M39.3 TS1M0
Microsoft® Windows® for x649.219.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Datacenter Edition9.219.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Enterprise Edition9.219.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 Standard Edition9.219.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2003 for x649.219.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 20089.219.39.2 TS2M39.3 TS1M0
Microsoft Windows Server 2008 for x649.219.39.2 TS2M39.3 TS1M0
Microsoft Windows XP Professional9.219.39.2 TS2M39.3 TS1M0
Windows 7 Enterprise 32 bit9.219.39.2 TS2M39.3 TS1M0
Windows 7 Enterprise x649.219.39.2 TS2M39.3 TS1M0
Windows 7 Home Premium 32 bit9.219.39.2 TS2M39.3 TS1M0
Windows 7 Home Premium x649.219.39.2 TS2M39.3 TS1M0
Windows 7 Professional 32 bit9.219.39.2 TS2M39.3 TS1M0
Windows 7 Professional x649.219.39.2 TS2M39.3 TS1M0
Windows 7 Ultimate 32 bit9.219.39.2 TS2M39.3 TS1M0
Windows 7 Ultimate x649.219.39.2 TS2M39.3 TS1M0
Windows Vista9.219.39.2 TS2M39.3 TS1M0
Windows Vista for x649.219.39.2 TS2M39.3 TS1M0
64-bit Enabled AIX9.219.39.2 TS2M39.3 TS1M0
64-bit Enabled HP-UX9.219.39.2 TS2M39.3 TS1M0
64-bit Enabled Solaris9.219.39.2 TS2M39.3 TS1M0
HP-UX IPF9.219.39.2 TS2M39.3 TS1M0
Linux9.219.39.2 TS2M39.3 TS1M0
Linux for x649.219.39.2 TS2M39.3 TS1M0
Solaris for x649.219.39.2 TS2M39.3 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.